SGI Performance Co-Pilot 1.3

home *** CD-ROM | disk | FTP | other *** search

/ SGI Performance Co-Pilot 1.3 / SGI Performance Co-Pilot 1.3.iso / dist / dist6.4 / pcp.idb / usr / share / catman / u_man / cat1 / pmlc.z / pmlc

Wrap

Text File | 1997-04-03 | 17KB | 328 lines

PPPPMMMMLLLLCCCC((((1111)))) PPPPMMMMLLLLCCCC((((1111)))) NNNNAAAAMMMMEEEE ppppmmmmllllcccc - configure active Performance Co-Pilot pmlogger(s) interactively SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS ppppmmmmllllcccc [----eeeeiiii] [----hhhh _h_o_s_t] [----nnnn _n_a_m_e_s_p_a_c_e] [----zzzz | ----ZZZZ _t_i_m_e_z_o_n_e] [----PPPP | _p_i_d] DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN ppppmmmmllllcccc may be used to change which metrics and instances a ppppmmmmllllooooggggggggeeeerrrr(1) writes to an archive, the frequency with which the metrics are collected and whether the logging is mandatory, advisory, on or off. It also reports the current logging status of metrics and instances. ppppmmmmllllcccc may be used to control pmlogger instances on remote hosts as well as those on the local host. Normally ppppmmmmllllcccc operates on the default Performance Metrics Namespace (PMNS), however if the ----nnnn option is specified an alternative namespace is loaded from the file _n_a_m_e_s_p_a_c_e. If the ----PPPP option is specified, ppppmmmmllllcccc will attempt to start with a connection to the primary pmlogger on the local host. Alternatively, if _p_i_d is specified, a connection to the pmlogger instance with that process id will be attempted on startup. The ----hhhh option may only be used if ----PPPP or a _p_i_d is also specified. In that case ppppmmmmllllcccc will initially connect to the specified (remote) pmlogger instance on _h_o_s_t rather than the local host. If the connection to the specified pmlogger instance cannot be established, ppppmmmmllllcccc will start with no connection. These options typically allow the same file of ppppmmmmllllcccc commands to be directed to multiple pmlogger instances by varying the command line arguments. Note that ----PPPP, _p_i_d and ----hhhh are used only when making an initial connection to a pmlogger instance. They are not used as defaults if subsequent connections are made interactively (see the ccccoooonnnnnnnneeeecccctttt command below). By default, times reported by ppppmmmmllllcccc are displayed in the the local time of the machine where ppppmmmmllllcccc is running. If ----zzzz is specified, times will be displayed in the time zone of the pmlogger instance from which information is being obtained. If ----ZZZZ is specified, times will be displayed in the time zone specified by _t_i_m_e_z_o_n_e, which should be a valid time zone specification (see TTTTZZZZ in eeeennnnvvvviiiirrrroooonnnn(5) for details). Only one of ----zzzz or ----ZZZZ may be specified. If standard input is from a tty, ppppmmmmllllcccc is interactive, with prompts. The ----iiii flag may be used to force interactive behaviour, and would typically be used in conjunction with ----eeee to echo all command input on standard output. The following commands may be used: sssshhhhoooowwww [ llllooooggggggggeeeerrrrssss ] [ @@@@_h_o_s_t ] Displays which pmlogger instances are running on the local host (or _h_o_s_t, if specified). The process ids (pids) of all of the available pmlogger instances are shown. The primary pmlogger's is parenthesized as it may be referred to by the name "primary" as well PPPPaaaaggggeeee 1111 PPPPMMMMLLLLCCCC((((1111)))) PPPPMMMMLLLLCCCC((((1111)))) as by pid. ccccoooonnnnnnnneeeecccctttt _p_i_d [ @@@@_h_o_s_t ] ccccoooonnnnnnnneeeecccctttt pppprrrriiiimmmmaaaarrrryyyy [ @@@@_h_o_s_t ] Connects ppppmmmmllllcccc with the specified pmlogger process. Any existing connection to a pmlogger instance is closed first. Each pmlogger instance will accept at most one connection at a time, so if the connection is successfully established, your ppppmmmmllllcccc will be the only one controlling the pmlogger instance it is connected to. nnnneeeewwww vvvvoooolllluuuummmmeeee This command works only while a connection to a pmlogger instance is established. It tells the pmlogger to close the current volume of the log and open a new volume. Closed volumes may be archived, e.g. as part of a regular log management procedure to control the size of the physical log files. ssssttttaaaattttuuuussss This command works only while a connection to a pmlogger instance is established. It prints information about the state of the pmlogger instance and its associated log. ttttiiiimmmmeeeezzzzoooonnnneeee llllooooccccaaaallll | llllooooggggggggeeeerrrr | """"_t_i_m_e_z_o_n_e"""" This command sets the time zone used when times are printed. llllooooccccaaaallll means use the time zone of the machine that ppppmmmmllllcccc is running on. llllooooggggggggeeeerrrr means use the time zone of the machine where the pmlogger instance is running. Alternatively an explicit _t_i_m_e_z_o_n_e enclosed in quotes may be supplied (refer to TTTTZZZZ in eeeennnnvvvviiiirrrroooonnnn(5) for details). The default time zone is llllooooccccaaaallll unless one of the ----zzzz or ----ZZZZ options was supplied on the command line when ppppmmmmllllcccc was started. fffflllluuuusssshhhh This command works only while a connection to a pmlogger instance is established, and requests the pmlogger instance to flush to disk all buffers associated with the current archive. For old-timers, ssssyyyynnnncccc is a synonym for fffflllluuuusssshhhh. hhhheeeellllpppp Displays a summary of the available commands. hhhh and ???? are synonyms for hhhheeeellllpppp. qqqquuuuiiiitttt Exits from ppppmmmmllllcccc. The remaining commands query and change the logging state of metrics and instances. They will work only if ppppmmmmllllcccc has a connection to a pmlogger instance. Metrics may be specified as fully qualified names (e.g. hinv.ncpu) or subtrees of the Performance Metrics Name Space (PMNS) (e.g. hinv) which are expanded to include all metrics in the subtree (e.g. hinv.ncpu, hinv.cpuclock, etc.). Lists of metrics may be specified by enclosing them in braces with spaces (or a comma) between metrics (e.g. {hinv.ncpu hinv.ndisk}). Subtrees of metrics may be included in such PPPPaaaaggggeeee 2222 PPPPMMMMLLLLCCCC((((1111)))) PPPPMMMMLLLLCCCC((((1111)))) lists. Each individual metric specification may further be qualified with a space (or comma) separated list of instances in square brackets (e.g. irix.kernel.all.load["1 minute", "5 minute"]). External instance names or numeric internal instance identifiers or both may be used in the same list (e.g. sample.colour.[red,1,"blue"]). If an instance qualification is applied to a subtree of the PMNS all of the metrics in the subtree must have the same instance domain. Instance qualifications may not be applied to entire lists of metrics but may appear inside such lists. If no instances are specified for a metric, all instances are used. All instances means all instances available at the time the pmlogger instance in question fetches the metrics for logging. If an instance domain changes over time this is not always the same as the set of instances displayed by ppppmmmmllllcccc, which can only display the currently available instances. To prevent unintentional errors, only the instances that are currently available to ppppmmmmllllcccc may appear in instance specifications. qqqquuuueeeerrrryyyy _m_e_t_r_i_c_l_i_s_t The current logging state of each metric (and instances, where applicable) in _m_e_t_r_i_c_l_i_s_t is displayed. This includes the logging state (e.g. on, maybe, off) and the logging interval for each metric (and instances) requested. The following abbreviations pertaining to metrics (and instances) may appear in the output: aaaaddddvvvv, advisory; mmmmaaaannnndddd, mandatory; nnnnllll, not in the log; nnnnaaaa, in the log but not currently available from it's Performance Metrics Domain Agent (PMDA). Where appropriate, an instance name will appear last on a line preceded by its numeric internal instance identifier. [ lllloooogggg ] mmmmaaaannnnddddaaaattttoooorrrryyyy oooonnnn _i_n_t_e_r_v_a_l _m_e_t_r_i_c_l_i_s_t This form of the lllloooogggg command turns on logging for the metrics (and any instances) in _m_e_t_r_i_c_l_i_s_t. _i_n_t_e_r_v_a_l specifies how often the specified metrics/instances should be logged. oooonnnncccceeee indicates that the metrics/instances should appear at most once in the log. More often one would use the optional keyword eeeevvvveeeerrrryyyy followed by a positive number and one of mmmmiiiilllllllliiiisssseeeeccccoooonnnndddd (or mmmmsssseeeecccc), sssseeeeccccoooonnnndddd (or sssseeeecccc), mmmmiiiinnnnuuuutttteeee (or mmmmiiiinnnn), hhhhoooouuuurrrr or their plurals. Internal limitations require the _i_n_t_e_r_v_a_l to be smaller than (approximately) 74 hours. An _i_n_t_e_r_v_a_l value of zero is a synonym for oooonnnncccceeee. [ lllloooogggg ] mmmmaaaannnnddddaaaattttoooorrrryyyy ooooffffffff _m_e_t_r_i_c_l_i_s_t This tells the pmlogger instance not to log any of the metrics/instances in _m_e_t_r_i_c_l_i_s_t. [ lllloooogggg ] mmmmaaaannnnddddaaaattttoooorrrryyyy mmmmaaaayyyybbbbeeee _m_e_t_r_i_c_l_i_s_t This tells the pmlogger instance to honour any subsequent advisory logging requests for the metrics/instances in _m_e_t_r_i_c_l_i_s_t. If the current logging state of the metrics/instances is mandatory (either on or off) the new state will be set to maybe (effectively advisory off). If the current state of the metrics/instances is already PPPPaaaaggggeeee 3333 PPPPMMMMLLLLCCCC((((1111)))) PPPPMMMMLLLLCCCC((((1111)))) advisory (either on or off) the state(s) for the metrics/instances will remain as they are. [ lllloooogggg ] aaaaddddvvvviiiissssoooorrrryyyy oooonnnn _i_n_t_e_r_v_a_l _m_e_t_r_i_c_l_i_s_t [ lllloooogggg ] aaaaddddvvvviiiissssoooorrrryyyy ooooffffffff _m_e_t_r_i_c_l_i_s_t Advisory logging is only applicable if the last logging state specified for a metric/instance was "mandatory maybe" (which permits subsequent advisory logging control) or if the logging state is already advisory. These two forms of statement turn advisory logging on or off (respectively) for the specified metrics/instances. The interpretation for _i_n_t_e_r_v_a_l is as above for the mmmmaaaannnnddddaaaattttoooorrrryyyy case. There is no continuation character required for commands that span lines. The word aaaatttt may be used interchangeably with @@@@. A request to log all instances of a metric will supersede any prior request to log either all or specific instances of a metric (if the request specifies a permissible transition in the logging state). A request to log specific instances of a metric when all instances of a metric are already being logged is refused by ppppmmmmllllooooggggggggeeeerrrr. SSSSEEEEEEEE AAAALLLLSSSSOOOO ppppmmmmllllooooggggggggeeeerrrr(1), ppppmmmmdddduuuummmmpppplllloooogggg(1) DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS Most error or warning messages are self-explanatory. A message of the form Warning: unable to change logging state for... followed by a list of metrics (and possibly instances) indicates that ppppmmmmllllooooggggggggeeeerrrr refused the request for the metrics (and instances) that appear. Any metrics (and instances) that were specified but don't appear in the message have had their logging state updated successfully (no news is good news). Usually this warning results from requesting advisory logging when a mandatory control is already in place, or requesting logging for specific instances when all instances are already being logged. CCCCAAAAVVVVEEEEAAAATTTT If all instances of a metric are being logged and a request is made to log specific instances of the metric with the same state and frequency, the request may appear to succeed, even though ppppmmmmllllooooggggggggeeeerrrr has refused the request. This is not normally a problem, as the required information will still be placed into the log by ppppmmmmllllooooggggggggeeeerrrr. However in the case where the metric is to be logged once, the outcome is not what might be expected. When ppppmmmmllllooooggggggggeeeerrrr receives a request to log a metric once, it places the current value(s) of the metric into the log as soon as it can, regardless of whether the metric is already in the log. This may be used to force values into the log. When a request to log specific instances of a metric arrives and is refused because all instances of the metric are already being logged, ppppmmmmllllooooggggggggeeeerrrr does not place PPPPaaaaggggeeee 4444 PPPPMMMMLLLLCCCC((((1111)))) PPPPMMMMLLLLCCCC((((1111)))) values for the instances requested into the log. It returns the current logging state for each instance requested to ppppmmmmllllcccc. The requested and returned states are identical, so ppppmmmmllllcccc doesn't raise an error as it should. To ensure that only certain instances of a metric are being logged, one should always turn off logging for all instances of the metric prior to turning on logging for the specific instances required. PPPPaaaaggggeeee 5555